Fix for content-type header with charset#110
Fix for content-type header with charset#110nithin-murali-arch wants to merge 1 commit intozerodha:masterfrom
Conversation
Issue with content-type header with [email protected] where the content-type header is application/json;charset=utf8 which breaks responses.
|
The fix is working |
|
I've implemented this fix for all content-type headers (including |
|
@ranjanrak . Don't open source stuff if you're not able to respond on time to fix issues. Look at the diff, where is text/csv there? - This is for "this was missing in your PR" |
You can refer to the implementation in lib/connect.ts at line 264. I have clearly mentioned in my earlier reply, if you're following the pattern( |
|
I'm not here to debate on the maintainability or my PR. Im here to talk about the issue I faced, and your unnecessary comment on "what I missed". I wrote a PR for the issue I faced, its not my job to search your repo for where else it needs to be fixed. You're a for profit venture, and this project is for profit. You're not doing this out of good will, remember that. |
Issue with content-type header with [email protected] where the content-type header is application/json;charset=utf8 which breaks responses.